Unified navigation shell user interface

ABSTRACT

A user interface for navigating among screens on a personal computer. The screens, which include layers of a shell user interface and various locations within applications, are presented as pages. In addition, commands and help information of an application are presented as a web of command pages. To this end, a unit of measure, called a “place” is defined. In general, an application is a place, and separate documents within an application may also define a place. Separate command windows and dialog boxes within an application or a document typically do not define a place. Backwards navigation takes the user to the previous place, and forward navigation (if possible) takes the user to the next place. Because the underlying data for a page may change between an initial visit to a page and navigation back to the page, data objects and page code are maintained separately, and are combined only when a request for a page is made.

FIELD OF THE INVENTION

The present invention generally relates to computer systems, and moreparticularly to a graphical user interface for a computer operatingsystem.

BACKGROUND OF THE INVENTION

A contemporary operating system, such as Microsoft Corporation'sWindows® 98 operating system, provides many different ways to navigatebetween and within applications on a computer. For example, existinguser interfaces utilize double clicks, right clicks, menu pulls, OKbuttons, close boxes, and the like to open and close applications, ordialog boxes within applications. If more than one application isopened, a user may be presented with multiple windows, which may becomecomplex and is often difficult to understand for many users,particularly a novice user.

Another problem that users encounter is that it is often difficult tofind documents that the user had previously accessed, or find the samepoint (e.g., menu or dialog) within an application that the user hadpreviously reached. A closed document and/or application suddenlydisappears from the screen, requiring that a user know its location orsome other way to return to the application and/or document at a latertime. The problem is exacerbated by the fact that so many documentsand/or applications are launched from different locations. For example,links to applications and documents may be presented on the user'sdesktop. Also, the Start button provides navigation via a pop-up menu toapplications and recent documents, and a task bar provides an icon foreach currently running application. The various options for accessingrecent documents and applications may not be logical for a user, whichmay make finding a particular recent document or application difficultand confusing.

Users also often have difficulty understanding how to navigate tocommands within an application. For example, existing applicationsutilize icons on tool bars, menu pulls, dialog boxes, and the like toprovide access to commands that are available for the application. Auser often finds the large number of icons and pull-down menu options tobe overwhelming. Many times, the symbols used on the icons are often notthat suggestive of the function of the command. Moreover, for drop-downmenus and dialog boxes, the commands are typically presented as one ormore words that are often not sufficiently descriptive of the functionprovided by the command. To discover the function (or find theappropriate command button), a user may need to consult helpinformation. The help information is provided in a separate dialog boxand/or window, and finding the appropriate help topic about the commandin question may be difficult. Navigating through all of these optionsmay be complex, and a user may not be able to access, or may not even beaware of, a variety of commands available in an application.

SUMMARY OF THE INVENTION

The present invention relates generally to a user interface fornavigating among screens on a personal computer. The user interfaceprovides back and forward buttons for navigating across a large range ofscenarios and interactions offered on the computer.

Existing web browsers, such as Microsoft Corporation's InternetExplorer, provide back and forward buttons for stepping back and forwardamong screens accessed by a user. However, these controls are onlyavailable within the context of the web browser application. With therelease of Microsoft Corporation's Windows 98, these controls wereextended to a limited set of scenarios and places within the operatingsystem (e.g., Windows Explorer). However, navigation betweenapplications (and often within the applications) still required movementbetween, and opening and closing of, multiple windows and/or dialogboxes. In contrast, the back and forward navigation of the presentinvention provides movement between pages or locations in differentapplications. To this end, a unit of measure, called a “place” isdefined. In general, an application is a place, and separate documentswithin an application may also define a place. Separate command windowsand dialog boxes within an application or a document typically do notdefine a place. Backwards navigation takes the user to the previousplace, and forward navigation (if possible) takes the user to the nextplace.

To facilitate forward and backward navigation, a global travel logmaintains a queue of visited places. Animations may be provided so thata user is aware that a navigation between places is occurring, which maynot be readily apparent to a user when navigating between places in thesame application. The animations may also provide an indication of thenavigation direction, e.g., backward.

In addition to the global travel log, a separate travel log ismaintained for each of the applications that have been run on thecomputer. What is entered into the travel log for each application maybe specified by the application. The travel log may be utilized tonavigate among the places visited within the application, for examplethrough a drop-down menu or a separate page.

When a user navigates away from a page, the page code (i.e., thecode/static data that implements a page) is maintained separately fromthe data (the document or objects which the page code is bound to,editing, or viewing). This is because the underlying data for a placemay be applied to many page codes, and the data should maintain itsidentity across all pages.

Data objects and page code are maintained separately, and are combinedonly when a request for a place is made. To this end, when a navigationaway from a page is made, information about the place is saved in theform of a Persistent Application Page, which includes a pointer to thepage code, and the place's View State, which includes information aboutthe view that is to be shown (“view information”) and a persistentreference to the data, in the form of a moniker. The PersistentApplication Page, or information about the Persistent Application Page,is written into the travel log or logs for each place.

To retrieve a place as a result of a request via the shell userinterface (e.g., by backward navigation via selecting the “Back”button), the Persistent Application Page is called, and, in return, themoniker retrieves the associated data object and view information andbinds it to the page code. The view information may be provided as apart of the moniker, metadata associated with the data object, or via aregistry of data objects and page views. The data object is bound to thepage code to produce an instance of the page in accordance with the viewinformation, and the screen display is updated to return the user to theselected place.

Another aspect of the present invention is directed to convertingcommands and help information of an application (presently presented indialog boxes, pop-up menus, and the like) into a web of pages. To thisend, each application has command information defined therewithaccording to a defined command schema. In the schema, commands aregrouped into command groups. Each command group and command may includethe following fields: a short name (terse), a long name (verbose),verbose descriptive information, a small icon, a large icon, a list ofapplication contexts for which the command is valid, and an alias name,which may help find the command in a search. Command groups also have alist of commands and/or other command groups that belong to the commandgroup.

The command schema enables a web of pages to be constructed from thecommand groups and commands. For example, if a user clicks on a commandgroup, a page is constructed showing the commands and other commandgroups, if any, listed for that command group. The page will also showinformation from the fields of the command group. For example, theverbose descriptive information may be shown on the same rendered pageas a short name for a command, and may thus provide help informationwhich presently is only available via a separate dialog box or window.

To restrict the scope of the particular pages in accordance with auser-specified search string, a “filter” may be set. To facilitate usernavigation among the web of pages, the pages can also include “links”,which are pointers to other commands or command groups (i.e., anothernode within the tree defined by the command group/command hierarchy). Asa result of selecting (e.g., clicking on) a link, a command Otheradvantages will become apparent from the following detailed descriptionwhen taken in conjunction with the drawings, in which:

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram representing a computer system into which thepresent invention may be incorporated;

FIG. 2 is a block diagram representing a general architecture for anavigation tool in accordance with the present invention;

FIG. 3 is a representation of a page hierarchy for a multiple page userinterface in accordance with the present invention;

FIG. 4 is a block diagram representing creation of a second pageinstance from a first page instance in accordance with the presentinvention;

FIG. 5 is a representation of a running data object for use in thepresent invention;

FIG. 6 is a representation of a rendered page for the user interface ofFIG. 2;

FIG. 7 is a representation of a drop-down recent page list for the pageof FIG. 6;

FIG. 8 is a representation of steps in an exemplary navigation sequenceas tracked in accordance with the present invention;

FIG. 9 is a representation of steps in a navigation sequence and theeffects of those steps on a running applications list in accordance withone aspect of the invention;

FIG. 10 is a representation of a screen shot of a recent places page inaccordance with the present invention;

FIG. 11 is a representation of a rendered recent applications page inaccordance with the present invention;

FIG. 12 is a representation of steps in a navigation sequence inaccordance with an aspect of the present invention;

FIG. 13 is a block diagram representing assembly of a command page inaccordance with an aspect of the present invention;

FIG. 14 is a representation of command node tree formed in accordancewith an aspect of the present invention;

FIG. 15 a representation of a rendered command page in accordance withthe present invention;

FIG. 16 a representation of an alternate embodiment of a renderedcommand page;

FIG. 17 is a flow diagram generally representing steps for navigatingvia a shell user interface in accordance with one aspect of the presentinvention;

FIG. 18 is a flow diagram generally representing steps forreinstantiating a page instance in accordance with one aspect of thepresent invention; and

FIG. 19 is a flow diagram generally representing steps for creating acommand page in accordance with one aspect of the present invention.

DETAILED DESCRIPTION

Exemplary Operating Environment

FIG. 1 and the following discussion are intended to provide a briefgeneral description of a suitable computing environment in which theinvention may be implemented. Although not required, the invention willbe described in the general context of computer-executable instructions,such as program modules, being executed by a personal computer.Generally, program modules include routines, programs, objects,components, data structures and the like that perform particular tasksor implement particular abstract data types.

Moreover, those skilled in the art will appreciate that the inventionmay be practiced with other computer system configurations, includinghand-held devices, multi-processor systems, microprocessor-based orprogrammable consumer electronics, network PCs, minicomputers, mainframecomputers and the like. The invention may also be practiced indistributed computing environments where tasks are performed by remoteprocessing devices that are linked through a communications network. Ina distributed computing environment, program modules may be located inboth local and remote memory storage devices.

With reference to FIG. 1, an exemplary system for implementing theinvention includes a general purpose computing device in the form of aconventional personal computer 20 or the like, including a processingunit 21, a system memory 22, and a system bus 23 that couples varioussystem components including the system memory to the processing unit 21.The system bus 23 may be any of several types of bus structuresincluding a memory bus or memory controller, a peripheral bus, and alocal bus using any of a variety of bus architectures. The system memoryincludes read-only memory (ROM) 24 and random access memory (RAM) 25. Abasic input/output system 26 (BIOS), containing the basic routines thathelp to transfer information between elements within the personalcomputer 20, such as during start-up, is stored in ROM 24. The personalcomputer 20 may further include a hard disk drive 27 for reading fromand writing to a hard disk, not shown, a magnetic disk drive 28 forreading from or writing to a removable magnetic disk 29, and an opticaldisk drive 30 for reading from or writing to a removable optical disk 31such as a CD-ROM or other optical media. The hard disk drive 27,magnetic disk drive 28, and optical disk drive 30 are connected to thesystem bus 23 by a hard disk drive interface 32, a magnetic disk driveinterface 33, and an optical drive interface 34, respectively. Thedrives and their associated computer-readable media provide non-volatilestorage of computer readable instructions, data structures, programmodules and other data for the personal computer 20. Although theexemplary environment described herein employs a hard disk, a removablemagnetic disk 29 and a removable optical disk 31, it should beappreciated by those skilled in the art that other types of computerreadable media which may store data that is accessible by a computer,such as magnetic cassettes, flash memory cards, digital video disks,Bernoulli cartridges, random access memories (RAMs), read-only memories(ROMs) and the like may also be used in the exemplary operatingenvironment.

A number of program modules may be stored on the hard disk, magneticdisk 29, optical disk 31, ROM 24 or RAM 25, including an operatingsystem 35, (including a file system therein and/or associatedtherewith), one or more application programs 36, other program modules37 and program data 38. A user may enter commands and information intothe personal computer 20 through input devices such as a keyboard 40 anda pointing device 42. Other input devices (not shown) may include amicrophone, joystick, game pad, satellite dish, scanner or the like.These and other input devices are often connected to the processing unit21 through a serial port interface 46 that is coupled to the system bus,but may be connected by other interfaces, such as a parallel port, gameport or universal serial bus (USB). A monitor 47 or other type ofdisplay device is also connected to the system bus 23 via an interface,such as a video adapter 48. In addition to the monitor 47, personalcomputers typically include other peripheral output devices (not shown),such as speakers and printers.

The personal computer 20 may operate in a networked environment usinglogical connections to one or more remote computers, such as a remotecomputer 49. The remote computer 49 may be another personal computer, aserver, a router, a network PC, a peer device or other common networknode, and typically includes many or all of the elements described aboverelative to the personal computer 20, although only a memory storagedevice 50 has been illustrated in FIG. 1. The logical connectionsdepicted in FIG. 1 include a local area network (LAN) 51 and a wide areanetwork (WAN) 52. Such networking environments are commonplace inoffices, enterprise-wide computer networks, intranets and the Internet.

When used in a LAN networking environment, the personal computer 20 isconnected to the local network 51 through a network interface or adapter53. When used in a WAN networking environment, the personal computer 20typically includes a modem 54 or other means for establishingcommunications over the wide area network 52, such as the Internet. Themodem 54, which may be internal or external, is connected to the systembus 23 via the serial port interface 46. In a networked environment,program modules depicted relative to the personal computer 20, orportions thereof, may be stored in the remote memory storage device. Itwill be appreciated that the network connections shown are exemplary andother means of establishing a communications link between the computersmay be used.

Unified Navigation Shell User Interface

The present invention provides a navigation system 60 for a computersystem such as the computer system 20. As described below, thenavigation system 60 provides a shell user interface 62 that facilitatesback and forth navigation between and within applications on thecomputer system 20.

FIG. 2 shows an architecture for the navigation system 60 in accordancewith the present invention. Although the navigation system 60 is shownas being installed in the computer system 20, components of thenavigation system as described herein may be distributed among aplurality of computer systems. In addition, some or all of the variouscomponents referenced herein may be combined with or included withinother components, while others may be separate from one another and maybe appropriately invoked as needed.

The navigation system 60 includes a shell component 64 associated withthe shell user interface 62. The shell component 64 is integrated into(or alternatively is external to and associated with) the operatingsystem 35. The operating system 35 also includes a renderer, such as anXML or HTML interpreter 63, having network access software.Alternatively, the interpreter 63, may be external to the operatingsystem 35.

In accordance with one aspect of the present invention, the shell userinterface 62 includes multiple layers (e.g., organized in a hierarchicalweb) of pages to organize and display links to local and remotedocuments, programs, web links, tasks, services, devices, and the like.At the top level of the multiple-page shell user interface 62, a startpage 65 (FIG. 3) provides access via hyperlinks to lower order pages 70₁-70 _(G), as well as a number of local and remote documents 67 ₁-67_(H), web locations 68 ₁-68 _(J), and programs 69 ₁-69 _(L). Thehyperlinks are displayed as headings, titles, icons, or the like, theselection of which provides access (via the shell component 64) toeither a lower order page or local and/or remote programs, documents,web sites, services, or devices. The lower order pages 66 ₁-66 _(G)preferably provide access via hyperlinks to sub-pages and more narrowlyscoped documents, web locations, and programs. The sub-pages may providefurther hyperlinks, and so forth. A shell user interface 62 is describedin U.S. Attorney docket no. 2310, entitled “Multiple-Page Shell UserInterface”, filed concurrently herewith, and incorporated herein byreference.

In addition to the multiple pages 65, 66 ₁-66 _(G) of the shell userinterface, the programs and/or applications on the computer system 20present their content and functionality to the user via pages 79 ₁-79_(R). The applications are thus represented by an arrangement of pages79 that manifest the functionality of the application. For example,various functions of the application may be divided into tasks, with oneor more separate task pages provided for each of the tasks. Tasks andtask pages are further described in the “Multiple-Page Shell UserInterface” application incorporated above. In addition to the task pagesfor an application, as is described further below, the various commandsalong with their corresponding help information and other commandrelated information for the applications are preferably organized intoseparate pages (e.g., one page per command).

The shell user interface 62 facilitates navigation among and betweenpages 65, 66 ₁-66 _(G) of the shell user interface, pages of theapplications, and the command/help information pages. For example, viathe shell user interface 62 of the present invention, a user cannavigate from an application page 79 to a command page, back to theapplication page, and then to the start page 65.

The pages described herein are preferably HTML (Hypertext MarkupLanguage) pages. HTML-created pages permit easy embedding of hyperlinksto web-based URLs or local references, and editing by a designer or auser. Note, however, there is no intention to limit the presentinvention to HTML, as virtually any page format language, e.g., XML(Extensible Markup Language) or DHTML (Dynamic HTML) or other pagecreation mechanism will suffice. A renderer (e.g., the interpreter 63)provides the mechanism to display the pages. If a format other thanHTML, XML, or DHTML is used, then an appropriate mechanism for renderingthat page format may be provided on the personal computer 20.

One possible default setting for the start page 65, the pages 66 ₁-66_(G), and the pages of the applications is maximization to the entirescreen, so that the user is presented with a large, easy-to-readdisplay. However, the start page 65 and the other pages may be sized bya user or a designer so that multiple windows or layered portionsthereof can be simultaneously displayed.

Returning now to FIG. 2, the shell component 64 is associated with aretrieval mechanism 70. As is described further below, when a request ismade by the shell user interface for a page, the retrieval mechanism 70accesses information related to that page in a PAP (PersistentApplication Page) database 71, an Object View Registry 72, and/or aRunning data object Table 73. Based upon that information, anappropriate page code 74 ₁-74 _(M) (e.g., including the HTML tags orstatic data that is used to implement a page), and page data 76 or 78(e.g., a document or data object that is implemented by the page code)are retrieved. For ease of reference, the data, document, object or thelike to which the page code is bound (e.g., for viewing or editing) isreferred to herein as a “data object” 76 or 78. The data objects may beeither running data objects 76 ₁-76 _(K) or non-running (i.e.,noninstantiated) data objects 78 ₁-78 _(N). A noninstantiated dataobject 78, when instantiated, becomes a running data object 76. Therunning data objects 76 ₁-76 _(K) are preferably stored withinhigh-speed memory (e.g., a RAM cache 75), and the noninstantiated dataobjects 78 ₁-78 _(N) are stored in persistent memory such as filestorage (e.g., one or more hard disk drives 27).

As represented in FIG. 4, an appropriate page code 74 and associatedrunning data object 76 are combined to form a viewable page instance 80.In accordance with one aspect of the present invention and as isdescribed further below, a global recent pages queue 81 maintainsinformation about selected page instances 80 that have been displayed bythe computer system 20. A plurality of application queues 82 ₁-82 _(P)are also provided for maintaining information about selected pageinstances 80 that have been displayed by particular applications, i.e.,a separate queue 82 ₁-82 _(P) is maintained for each application.

The present invention also provides a search engine 88 that isassociated with the shell component 64. As is described further below,in accordance with a query sent via the shell user interface 62, thesearch engine 88 references an annotation database 90, which includesannotation information regarding the data objects 76 and 78.

Page Codes and Data Objects

As described above, a page instance 80 is formed by combining page code74 with a running data object 76. To this end, the page instance 80 is avisible instance of a binding of the page code 74 and the running dataobject 76. Preferably, the page codes 74 are stored separately from thedata objects 76 or 78. This separation permits more than one page code74 to be applied to the same data object 76 so as to form separate pageinstances of the same data, with the data object maintaining itsidentity across all page instances. That is, a data object 76 modifiedwithin one page code 74 is available, with the modifications, to otherpage codes. Likewise, a single page code 74 may be applied to more thanone data object 76 or 78.

When a page instance 80 ₁ (FIG. 4) is saved by the computer system 20,information about the page instance 80 ₁ is captured in the form of aPersistent Application Page (“PAP”) 92. The Persistent Application Page92 may be saved to the PAP database 71, for example, and represents thebinding of the data object 76 to that page instance 80. A page instance80 may be saved in a variety of ways, such as explicit saving by a user,automatic saving by an application, or implicit saving by an action viathe shell user interface 62 (described further below).

As can be seen in FIG. 4, the page instance information in thePersistent Application Page 92 includes a pointer 93 to the page code 74for the page instance 80 ₁, and a persistable form of the page instance,referred to as a View State 94. The pointer 93 is a reference to thelocation of the page code 74, such as in the form of an Uniform ResourceLocator (URL) or the like. The View State 94 is unique to the particularpage instance 80 ₁, and includes a view selector 95 and a persistentreference to the data object 76 or 78, in the form of a moniker 96. Asis described further below, the view selector 95 manages a decisionprocess regarding the type of view that is to be provided and thecondition of that view (collectively the “view state”) for a particularpage instance 80.

After the page instance 80 ₁ is no longer viewable, to request a view ofthe page (i.e., a second page instance 802 of the same data object 76bound to the same page code 74), the retrieval mechanism 70 referencesthe Persistent Application Page 92. The pointer 93 identifies the pagecode 74, and the moniker 96 accesses the respective data object 76 or78. The running data object 76 is then bound to the page code 74, andthe second page instance 80 ₂ is displayed according to view informationselected by the view selector 95. If the data within the data object 76has changed since displaying the first page instance 80 ₁, the changeddata will be displayed in the second page instance 80 ₂ (assuming thedata is part of the visible portion of the page instance 80 ₂). As isdescribed further below, the view selector 95, in conjunction with othersources, may dictate that the view of the second page instance 80 ₂ bedifferent than the view of the first page instance 80 ₂.

For a moniker 96 to bind to a data object 76, the data object needs tobe running, i.e., the data object must be a running data object 76within the cache 75. To this end, monikers 96 work in conjunction withthe Running data object Table 73 to either create a new running dataobject 76 (i.e., instantiate a noninstantiated data object 78) or locatean existing running data object, as appropriate. The Running data objectTable 73 manages the lifetime of running data objects 76 and ensuresmapping between the moniker 96 and the appropriate running data object76. To this end, the Running data object Table 73 includes a hash tableof currently running data objects 76, keyed by their monikers 96.

The view selector 95 manages a decision process regarding the type ofview that is to be provided and the condition of that view (collectivelythe “view state”) for a particular page instance 80. As examples of viewstate information, an e-mail message object may be displayed in afull-page view or in a different short search-result view. A wordprocessing document may be presented in a maximized window with a viewof the document, or alternatively in a partially minimized window. Thebeginning of the document may be displayed, or some other portion of thedocument may be displayed, i.e., partially scrolled through thedocument. As is described further below, the view selector 95 mayinclude and may apply its own view state, or may apply view stateinformation maintained by another source. The view selector 95 ispreferably bound to the moniker 96, and is invoked when the monikerinitiates binding with the appropriate running data object.

While the view selector 95 is ultimately in control of how page views ona running data object 76 are created, a default page view for a runningdata object may be provided in a registry, such as the Object ViewRegistry 72. The Object View Registry 72 maintains a mapping betweendata objects (or data types) and default views for the objects. A new orcustomized view for any combination of a running data object data typeand a view category may be registered with the Object View Registry 72.The view selector 95 may apply the default view supplied by the ObjectView Registry 72, or may use other view information as described below.

A running data object 76 may include information about a default viewfor that object therein, and the view selector 95 may apply thatinformation in conjunction with, or to override, the default viewprovided in the Object View Registry 72. For example, a DataDescriptor98 (FIG. 5) may be maintained within or associated with (e.g., asmetadata) a data object 76 or 78. The DataDescriptor 98 preferablyincludes information that identifies the data object's class and/orprovides descriptive information about the object's data type, and, ifso, then the Object View Registry 72 may be used to match the class ortype information with an appropriate view. Alternatively, theDataDescriptor 98 may directly provide a view to override the defaultview in the Object View Registry 72.

The view selector 95 may include its own built-in view or views, whichthe moniker 96 may implement instead of the default view provided by theObject View Registry 72 or DataDescriptor 98 (if available). Inaddition, information about views may be saved into the annotationdatabase 90, and that information may be used by the view selector 95.

More particularly, sometimes information about data objects 76 or 78cannot be written into the data objects. For example, a data object maybe designated read-only. It may be desirable to maintain informationabout the data object, however, so that the information may be queriedby the computer system 20 or a user. To this end, the present inventionmaintains annotation data 102 (FIG. 5) associated with, but not writteninto, some of the data objects 76, 78. The annotation data 102 ismaintained in the annotation database 90, and may be accessed and/orqueried via the retrieval mechanism 70, the search engine 88, or anothercomponent if necessary. Examples of items that may be maintained in theannotation database 96 include text relevant to a free-text search orheuristically-recognized properties (e.g., author, subject, or type). Inaddition, cross-object relationships (e.g., embeddings or links) may bemaintained, which can be used to extend search logic (i.e., the searchfinds direct or close hits and returns the hits along with items thatare linked to the hits). Information may also be saved in the annotationdatabase 96 about the most recently used or the most frequently usedviews for a data object. This information may be used (e.g., by the viewselector 95) to determine an appropriate view for the page instance 80.A user may also generate information (e.g., electronic sticky notes,etc.) about a data object 76 or 78 that is added to the annotationdatabase 96.

Multiple monikers 96 may bind to the same running data object 76. Tomanage lifetimes of running data objects, each time a moniker 96 bindswith a running data object 76, the running data object's reference countis incremented. Likewise, when a binding with a moniker 96 is released,the reference count of the running data object 76 is decremented. When arunning data object's reference count becomes zero, it notifies theRunning data object Table 73, which can elect to flush the running dataobject 78 from the cache 75 according to some caching policy, forexample based upon available cache space and/or a most frequently usedalgorithm and/or the time the running data object 76 has been in thecache with a zero reference count.

For example, multiple monikers may bind to the same object for atwo-phase commit transaction context. A two-phase commit transactionrequires that all parties to a transaction sign off on the transactionbefore it is committed. Multiple monikers may also bind to a singlerunning data object 76 that changes in response to external events(e.g., stock quotes), is modified by one or more page codes 74, or ispart of a database with nontrivial record interdependencies. To managesuch occurrences, the present invention defines a protocol forsynchronizing access to a running data object 76. To this end, a moniker96 requests a running data object 76 for a cloned proxy to itself, whichexists only for the duration of a transaction. Several such proxyobjects can be tied to the same transaction context. A “commit” isatomic with respect to all transactions outside of the context. Proxyobjects can themselves be proxied; in effect, this allows for nestedtransactions.

As can be understood, view information may be provided by a variety ofsources, and the priority of the type of view to be shown may bedetermined as desired by a designer. However, in one implementation, itis preferred that the view information adopted by the view selector 95be substantially identical to the view information for the page instance80 that created the Persistent Application Page 92, so that a pageinstance created from the Persistent Application Page appearssubstantially the same as the original page instance.

Navigation Bar

A representation of a screen shot 98 for the shell user interface 62 isshown in FIG. 8. The screen shot 98 includes a navigation bar 100extending along the top of the screen, and a page instance viewing area102 that extends across the remaining portion of the screen.Alternatively, the navigation bar 100 may be located elsewhere on thescreen, e.g. on the bottom or sides, with the user given the option tochoose. In a preferred embodiment, the navigation bar 100 is visiblethrough most of the range of scenarios and interactions offered on thecomputer system 20, although an auto-hide feature or the like may beimplemented. The page instance viewing area 102 provides a location fordisplay of one or more of the pages 65, 66 of the shell user interface62 or a current page instance 80 from an application or program. If morethan one page is displayed, the multiple pages may be layered, tiled, ormay be presented in another convenient manner.

The navigation bar 100 includes, at a far left side, a back button 104and a forward button 106. A start page link 108 is located on thenavigation bar 100, such as adjacent to the forward button 106. Arunning applications list 110, having a number of application links1121-1124 to applications or web sites (described further below), may belocated just the right of the start page link 108, and extends acrossthe navigation bar 100 to a middle portion of the right side of thenavigation bar 100. At the right end of the navigation bar 100, adjacentto the running applications list 110, is a recent applications page link114.

Some of the buttons may have drop-down menus or the like associatedtherewith. Such application links 112 may have a drop-down button (e.g.the drop-down button 115 in FIG. 7) adjacent thereto. As shown in FIG.7, selecting a drop-down button 115 opens a recent page menu 116 (FIG.7) for the corresponding application or web site. The recent page menu116 includes a number of recent page links 1181-1185, an applicationwebsite link 120, and a “More . . . ” link 122. Alternatively, therecent page menu may be caused to automatically open by moving thepointing device over the application link 112, possibly requiring thatthe pointer remain over the application link for a period of time beforeopening the menu 116. In any event, the application links 112 on thepage menu may then be selected.

Navigation Via the Navigation Bar

The back and forward buttons 104, 106 provide back and forth navigationacross a large range of pages that have been visited via the shell userinterface 62. To this end, a unit of measure, called a “place” isdefined. A place is a page instance 80 or a page 65, 66 in the shelluser interface 62 that includes information maintained in the globalqueue 81. The global queue 81 maintains information about the places,thereby forming a travel log of previously visited places. As describedbelow, the back and forward buttons enable the user to navigate amongplaces in the travel log.

Each application may determine which page instances 80 created by thatapplication are places for that application that can be logged. Asstated above, at least some of the applications that are accessed by theshell user interface 62 are presented as a web of pages that display thetasks, commands, help information, and other functionalities provided bythe application. Not all of these pages are necessarily maintained inthe global and/or application queues 80, 82. For example, page instances80 that are created from a particular task page may be included in theapplication queue 82 and/or the global queue 80, but dialog pages (e.g.,equivalent to a dialog box), may not be included.

The shell component 64 may define places for applications that weredeveloped prior to implementation of the shell user interface 62(“legacy applications”). For example, the shell component 64 may definethat a document or web page accessed via a legacy application defines aplace, but a dialog box does not. Some applications (e.g., MicrosoftCorporation's Word 2000) utilize a single document interface (SDI),wherein there is one window per document. For SDI applications, eachdocument may be defined by the shell component 64 as a separate place.Other applications (e.g., Microsoft Corporation's Photodraw photoediting program) utilize a multiple document interface (MDI), whereinthere is one top-level window and several lower-level (child) windowsbounded by the top level window. The shell component 64 may tag thechild windows as documents rather than dialog boxes, so that visits tomultiple child windows constitute separate places within the travel log,whereby the multiple child windows may be revisited via back and forwardnavigation. The back and forward buttons 104, 106 are then available fornavigation along with the display of the legacy application.

When a request for a legacy application is made via the shell userinterface 62, the legacy application sometimes provides calls to theshell component 64 that are not consistent with the unified navigationdescribed herein. For example, a legacy application may request aseparate window that would cover at least part of the navigation bar100. To address such calls from legacy applications, the shell component64 may suppress the calls and/or reroute the calls to other drawingfunctions of the shell component, so that, for example, the legacyapplication may be displayed, preferably maximized, in the page instanceviewing area 102 (FIG. 6).

Animations may be provided so that a user is aware that a navigationbetween places is occurring, which may not be readily apparent to a userwhen navigating between places in the same application. For example, anicon 126 (FIG. 6) may be provided in the navigation bar 100 and mayflash or the display may otherwise change state when a navigationbetween places occurs.

Each time a page instance 80 corresponding to a place is saved,information about that page instance 80 or that page instance'sPersistent Application Page 92 is written into the global travel queue81. In addition, information about the page instance 80 and/or thePersistent Application Page 92 is written into the application queue 82for the application. Alternatively, the Persistent Application Page 92itself may be written into the respective queues 81, 82.

The back and forward buttons 104, 106 may be used to navigate betweenplaces in the global queue 81. In general, selecting the back button 104navigates a user to the previous place in the global queue 81. Selectingthe forward button 106 navigates a user to the next place in a sequenceof places (if present). If a place is not available, a visual indication(e.g., gray out respective button) may be provided on the display.

To retrieve a page instance 80 as a result of a request via the shelluser interface 62 (e.g., by selecting the “back” button), the shellcomponent 62 accesses the global queue 81 to determine the appropriateplace based upon the current place. The Persistent Application Page 92is called and, in return, the moniker 96 retrieves the associatedrunning data object 76 and view selector 95 and binds it to the pagecode 74. The running data object 76 and the page code 74 are combined todisplay the page instance 80 in accordance with view informationdictated by the view selector 95. Note that although not shown, one ormore options (e.g., extra buttons and/or a drop-down menu) may beprovided to navigate multiple places in the queue with a single click.

An example of a simple navigation sequence 130 is shown in FIG. 8. Inthe navigation sequence 130, a shell user interface 62 displays sevenconsecutive pages 132-144. The pages 132-136 and 140-144 are places,however the page 138 is not a place and thus is not entered in theglobal queue. As a result, navigation using the back and forward buttons104, 106 navigates the user between displays of all the pages except forthe page 138 that is not a place. That is, in the present example,hitting the back button while the page 140 is displayed causes the page136 to be displayed instead of the page 138. Likewise, hitting theforward button while the page 136 is displayed navigates the user to thepage 140.

The start page link 108, which is preferably persistent on thenavigation bar 100, navigates the user to the start page 65. Informationabout the start page 65 is then written into the global queue 81. Theuser may then used the back button 104 to return to the previous place,or may select a hyperlink that is presented on the start page 65.

The running applications list 110 includes an application link 112 for adefined number of applications and/or web sites that have been recentlyvisited by a user, and have not been closed by the user. Someapplications that provide a plurality of services may provide aplurality of application links (e.g., an email program may provide anaddress list link, an inbox link, and/or a calendar link). Included inthe running applications list 110 is the presently displayed place.

The application links 112 may be represented as icons, headings, or thelike, or as thumbnail representations of the last place visited in therespective application or web site, with a representative icon or thelike representing the respective application or web site. The number ofapplication links 112 displayed in the running applications list 110 maybe fixed or variable (e.g., based on the current screen width). If thenumber is fixed, the application links 112 may shrink to fit the size ofthe running application list 110.

FIGS. 9A-9E represent one manner of maintaining the running applicationslist 110. In accordance with one embodiment of the present invention,upon start-up of the computer system 20, the applications list 110 (FIG.9B) is empty. Alternatively, application links 112 from the previoussession may be persisted in the running applications list 110. When afirst place 150 (FIG. 9A) is visited in a first application or web site,an application link 1121 representing that place (and the correspondingapplication or web site) is placed in the left-most location in therunning applications list 110. As additional places 152, 154 (FIG. 9A)are visited, if the running applications list 110 is not full, thenlinks 112 ₂ and 112 ₃ (FIG. 9B) are added (in order of navigation) tothe left side of the running applications list 110. Existing applicationlinks 112 index toward the right. This process continues until all ofthe available slots are filled (FIG. 9C).

When the running applications list 110 is full, visiting a new placecauses a new application link 112 to replace an old application link. Ifthe application or web site associated with the new application link 112₅ is already represented in the running applications list 110 (e.g., theplace 158 visited in FIG. 9A), then the new application link 112 ₅ mayreplace the old application link 112 ₁ for that application. That is,the more recently visited place 158 is represented by the applicationlink 112 ₅. The previous application link 112 ₁ is moved to the recentapplication page menu 116 (i.e., as one of the recent page links 118₁-118 ₅ in FIG. 7). The application link 112 ₅ is preferably shown as athumbnail representation of the more-recently visited place 158. If theapplication associated with the new application link 112 is notrepresented in the running applications list 110 (e.g., place 160visited in FIG. 9A), the new application link 112 ₆ (FIG. 9E) preferablyreplaces the least-recently-used application link 112 ₃ in the runningapplications list 110.

The running applications list 110 may be maintained using alternativeheuristics. For example, the running applications list 110 may bemaintained in strict temporal order. That is, application links 112 areadded on the left, and old items fall off the right side. This may betrue even if the same application is represented several times in therunning application list 110. Also, if desired, one or more slots in therunning applications list 110 can be determined by a most frequentlyused heuristic, which persists links to applications that are the mostfrequently used applications. In addition, if desired, a mechanism maybe provided by which a user locks the position of an application link112 in the running applications list 110.

As described above, if another place is visited within an application orweb site already represented on the running applications list, thatplace may become the current application link 112 representing theapplication or web site. If desired, however, when the runningapplications list is not full, the second place for the application mayrepresent a second application link 112 in the running applications list110. When the running applications list 110 becomes full and anadditional application or web site is visited, the two places may rollinto one application link 112 to permit room for a new application link.In addition, if desired, particular places in selected applications orweb sites (e.g., a document in a word processing application) mayrepresent a separate application link 112 in the running applicationslist 110. The application links 112 representing the particular placesare added and removed as if they were application links to separateapplications (e.g., according to the most-recently-used heuristic).

If an application or web site is closed, the application link 112 forthe application or web site is removed from the running applicationslist 110. The vacated slot in the running applications list 110 mayremain empty, or an application link 112 that had previously beendropped out of the running applications list may be added back to thelist (e.g., the most recently visited application that was dropped fromthe list). The application link 112 added back to the runningapplications list 110 may fill the previously empty slot, or may beadded to the right side of the list, indexing application links in listto the left, if necessary. Alternatively, the empty slot may remainblank until a new application is selected and the new application fillsthe blank location.

Occasionally, consecutive navigations via the back button 104 causes auser to navigate to an application that is no longer shown in therunning applications list 110. In doing so, an application link 112 forthat application or web site is placed back in the running applicationslist 110. The new application link 112 may be added according to aheuristic, e.g., take place of the least-recently-used application linkin the running applications list 110, be placed on the list inaccordance with a strict temporal order, or any other heuristic such asone described above.

As can be understood, a user that spends a lot of time surfing theInternet may quickly replace all application links 112 in the runningapplications list with new application links for recently visited websites. To prevent this from occurring, the number of application links112 directed to web sites may be limited to a particular number (e.g.,three), or other limitations may be placed on the links to web sitesthat are placed in the running applications list 110. For example, if auser is viewing web pages that are accessed via links from a portalwebsite, the story pages may be grouped in a single application link 112with the application link to the portal website. As another example, allwebsites/pages that are accessed via the same set of search results maybe grouped into one application link 112.

Returning to FIG. 7, selecting an application link 112 navigates to theplace (e.g., a web page or document) represented by that applicationlink. Likewise, selecting one of the recent page links 118 ₁-118 ₅ fromthe recent application page menu 116 navigates to the place representedby that recent page link. Selecting the application website link 120navigates to the web site for the application or the home page for a website.

Selecting the More link 122 navigates to a recent places page 162 (FIG.10), which displays links 164 to a number of recent places for theapplication or web site. The places may be maintained by the applicationqueue 82 for the respective application or web site. The links 164 maybe presented as list of headings, a group of icons, or the like, butpreferably are represented as thumbnail representations of the places.In the embodiment shown in FIG. 10, twenty links 164 ₁-164 ₂₀ are shown,but any number by be defined by a designer, the user and/or the sizingof the recent places page. If more places are available than displayed,a More link 166 enables navigation to additional places, which may bedisplayed on an additional page or pages.

Selecting the recent applications page link 114 navigates the user to arecent applications and web sites page 170 (FIG. 11). The recentapplications and web sites page 170 displays a defined number of links172 representing the most-recently-displayed applications and web sites.In the embodiment shown in FIG. 11, links 172 ₁-172 ₂₀ to the twentymost recent applications and web sites are shown. The links 172 may berepresented as a list of headings, groups of icons, or the like, butpreferably are displayed as thumbnail representations of theapplications or web sites. Selecting one of the links 172 displays therecent places page 162 for the application. Additional applications andweb sites may be viewed (e.g., via additional pages or a page) byselecting a More . . . link 174.

Travel Log Maintenance

As stated above, the global queue 81 maintains a travel log of previousplaces accessed by the shell user interface 62. Similarly, eachapplication queue 82 preferably maintains a travel log of previousplaces accessed by the respective application.

Certain sequences of navigations by the user interface 62 provide avariety of different options for maintenance of the travel log for theglobal queue 81 and/or an application queue 82. For example, FIG. 12shows a navigation sequence 176 between five places A, B, C, D, E in thefollowing order: A, B, C, D, C, E. Selecting the back button 104 (FIG.6) at the place E navigates to the place C. However, selecting the backbutton 104 at the place C provides a variety of alternatives. Forexample, if the global queue 81 maintains the travel log in a stricttemporal order, then four successive selections of the back button 104from the location C results a navigation as follows: D, C, B, A.Alternatively, a “pruning method” may be utilized for maintained thetravel log, in which navigations between two visits to a single placeare removed from the travel log. If the pruning method is used,selecting the back button 104 three consecutive times from the place Eresults in a navigation having the following order: E, C, B, A.

Another alternative for maintaining the travel log is a “single revisitmodel”. Under the single revisit model, places within a navigation areplaced in a temporal order, and duplications of places are removed fromthe temporal order. Thus, four successive selections of the back button104 from the place E results in a navigation as follows: E, C, D, B, A.

In one embodiment, the default maintenance for the travel logs is thesingle revisit model. However, some sequences of pages (e.g., wizardsand pages with a strong spoke and hub relationship) are better served bythe pruning method. Applications and/or web sites may define whichmaintenance heuristic is to be used for individual collections of pages.Alternatively, rules may be defined by the shell component 64 or thequeues 81, 82 that anticipate sequences of pages that are best served byan alternative heuristic. For example, the pruning method may beutilized as a default for navigations between web pages, but the singlerevisit model may be used at web site boundaries. As another example,wizards and pages with a strong spoke and hub relationship may be betterserved by the pruning algorithm for the travel log.

The shell component 64 may also access the queues 81 in response to aselection via the shell user interface 62 of something other than theback or forward buttons 104, 106. For example, if a link to anapplication is selected, the shell component accesses the queue 82 forthe application, and the most recent place for the application isaccessed. Alternatively, a default page for the application isdisplayed. As an example, if a user is in an email program preparing anemail for sending, navigates to a word processing document, and thenclicks on a link for email (provided on the navigation bar, forexample), accessing the application queue 82 directs the user back tothe email that is being prepared. Alternatively, the link may direct theuser to the Inbox for the email program (or may open the email programin another default page). A problem exists in the latter scenario if theInbox and the draft email are considered to be in the same applicationfor purposes of the travel log in that the single revisit model will notallow navigation via the back button 104 to the screen where the emailwas being prepared. A user would instead have to navigate to the screenvia the email application's travel log (i.e., as described below, viathe email application's recent application menu 116 or recent placespage 162).

The shell user interface 62 may be used in a multiple windowenvironment, i.e., there may be multiple instances of shell userinterfaces 62, each of which corresponds to a window. In such operation,the navigation bar 100 is preferably provided for each window. Aseparate travel log is maintained for each window, as well as a separaterunning applications list. If a legacy application is utilized, and thatlegacy application uses a floating window, then controls similar tothose in the navigation bar 100 may be presented in a window atop thefloating window. Preferably, an applications queue 82 specifically forthat application is utilized for navigation within the floating window.

In accordance with another multiple window embodiment, each applicationprogram that is running on the computer may be in a separate window. Insuch a mode, a navigation bar is preferably provided for each window.When utilizing the back and forward buttons 104, 106 at a first place, arequest for a second place displays the second place in the currentwindow if the second place is associated with the same applicationwindow as the first place. If the second place is associated with asecond application window (e.g., of another application), then selectingthe appropriate button 104, 106 navigates the user to the secondapplication window. The user may then navigate using the back and forthbuttons 104, 106 that are provided in the window for the secondapplication, which may, for example, navigate the user back to the firstapplication window, to a third application window, or to another placein the second application window.

As stated above, the present invention preferably utilizes an implicitsave feature that saves modifications to the data object 76 and/or viewinformation when a navigation away from a page instance 80 is made. Theimplicit save feature permits a user to navigate away from a pageinstance 80 without being concerned about losing revisions to theinformation in the page instance. For a legacy application that does notpermit implicit save, a dialog box or the like may be used to inform auser that a save should be made before a navigation occurs.

Presentation of Command and Help Information

Another aspect of the present invention is directed to convertingcommands and help information of an application (presently presented indialog boxes, pop-up menus, and the like) into a web of command pages.To this end, each application has command information defined therewithaccording to a defined command schema 180 (FIG. 13). In the commandschema 180, commands 182 are grouped into command groups 184, andattributes (“fields 186”) are defined for each of the commands andcommand groups. An assembly component 188 utilizes the command schema180 to construct a command page 190 or command pages.

The fields 186 represent, for example, items that may be displayed on acommand page that represent the command or the command group (e.g.,titles and icons), search terms for finding the command group in atextual search, verbose descriptive information about the command orcommand group, and the context in which the commands or command groupsmay be displayed (e.g., application pages). Note that the fields such asthe verbose description field may include textual, audio, audiovisual,graphical, animation, and/or other information (or links thereto)capable of being sensed by a user.

For example, the schema may include the following fields: Field NameData short name one or two word name long name short phrase verbosedescription short paragraph icon a toolbar icon search terms hidden textused for a command search Valid contexts application pages (contexts)for which the command is valid

As an example, the following fields may be defined for a “search”command for an email application: Field Name Data short name search longname search my mail verbose description This command will allow you tosearch through all of your mail and find any messages that are stillstored on your computer. You can view your mail by date, sender. Or, ifyou remember a word or phrase in the mail you're looking for, you cantype that in and see a list of only mail containing the text you'vespecified. icon <bitmap> search terms find, seek, view, look, see validcontexts all pages

A node tree 192 (FIG. 14) is constructed by the assembly component 188that represents commands 182 and command groups 184 that are availableto an application. Some command groups 184 include both commands 182 andcommand groups, while other command groups include only commands. Theassembly component 188 maps nodes of the node tree to particularcontexts in the application based upon the schema information.

When a user requests commands 182, or the application wants to show theuser some subset of the commands, the identifying parameters forbuilding a command page 190 are: 1) the current application context, and2) a node in the node tree 192 at which to begin the construction of thecommand presentation. Using the node tree 192, the assembly component188 programmatically constructs the command page 190 for a particularcontext of an application. The assembly component 188 walks the commandnode tree 192 and, by applying visual style templates to the command andcommand group fields 186, creates the command page 190. For example, acommand page may be constructed beginning from the node for the CommandGroup 3 in FIG. 14. The command page has the Commands 6-8, 12-14 andCommand Groups 3 and 5 available for display.

A “filter” 194 may be set, to restrict the scope of the commandinformation shown on the command page 190 in accordance with auser-specified search string. For example, the command page 190 may havebeen created in response to a search query directed to particularcommand information that is more limited than the commands available atthe context at which the request was made.

The assembly component 188 may also use a user's past history 196 ofcommand usage in order to customize the presentation (e.g., to emphasizefrequently used or recently used commands). Commands may be bubbled upon the command page 190 in accordance with the past history 196 (e.g.,as prominent icons). The assembly component 188 may also take intoaccount the applicability of the current selection to hide or emphasizeparticular commands or command groups. For example, if the user selectsa table, and then requests a command, an “add rows/columns” command maybubble up at the top of the command page 190.

When applying the visual style templates, in one implementation, theassembly component attempts to display the largest fields 186 possibleon the command page 190. For a context that provides a minimal number ofcommands 192, the “long name” 197 of all commands 192 may fit on thecommand page 190, along with the verbose information 198 (FIG. 15). Ifdesired, icons 199 may be bubbled up according to a heuristic (e.g.,user history, described further below). If a more extensive list is tobe displayed, the command groups may be represented as pull menus orpop-up menus, with the commands nested therein, or icons for thecommands may be presented.

The icons, short titles, and long titles may effect operation of theunderlying command, or may represent a link. These links are simplypointers to another node on the command graph. By clicking on such alink, the system navigates to another command page that is created asdescribed above.

A user may initiate construction of a command page in a number of ways.For example, a text-based search query may result in creation of acommand page 190. In addition, a link to a command page or pages that isrelevant to a particular context may be provided via a user interface(e.g., in the navigation bar 100). In accordance with one embodiment,right clicking (e.g., via the pointing device 42) on a particularlocation in a page instance 80 generates a command page scoped to thecontext of the page, and the applicability of the selection by thepointing device 42.

For example, if a user selects and right-clicks on text in a document ina word processing program, a list of pertinent commands related to theselected text are offered on the command page. For example, commands infont style command groups and justification command groups may bedisplayed. Because the font style commands are more pertinent to theselection of the text, the font style command group may be expanded intoFont, Size, Style commands, and the like, and the verbose descriptionmay be displayed for those commands. The justification commands may notbe as important for the selection (i.e., text), and therefore thejustification command group may be presented only as link (e.g., via anicon) to a second command page. On the other hand, if the user selectsand right clicks on a paragraph, the justification commands may expandand the font commands, which are still important, may also be expanded.However, a thesaurus link may be removed, since such a link applies toindividual words, not an entire paragraph.

In accordance with another embodiment, right clicking on a general areaof a document shown by an application page navigates the user to acommand page 200, where a thumbnail of the document is displayed in athumbnail window 201. A scope selection menu 202 is located just belowthe thumbnail window 201. The scope selection window 202 includes anumber of different items that may be selected on the page in thethumbnail window 200 (e.g., cursor selection, word selection, paragraphselection, page selection, and document selection).

In response to a user selecting a scope selection in the scope selectionwindow 202, the assembly component 188 creates a command and/or commandgroup display in a command pane 204. If the user selects another scopeselection, the assembly component points to a different node on thecommand node tree 192, and creates another display of commands and/orcommand groups ir accordance with the node selection.

Selecting the back button 104 while at the command page 190 and before acommit has been made to a command's operation may result in “undo”,“escape”, “save”, “OK”, “enter”, or may have no effect on the commandpage. A designer may define the result or backward navigation inaccordance with a desired outcome. Preferably, if a command page isdefined as a place by an application, navigating back to a command pagedoes not result in an “undo” of a committed command operation.

Although the assembly component 188 has been described with reference toassembling a command page 190, the assembly component may instead createa command window or dialog box to be presented in conjunction with anapplication page or other page displayed by the shell user interface 62.The command window is preferably sized so that it minimizes viewinterference of the page instance 80 being hosted by the shell userinterface 62. In addition, the assembly component 188 may present atoolbar having relevant icons for a selection and/or context.

Operation of the Present Invention

Turning now to an explanation of the operation of the present invention,FIG. 17 shows a general overview of a process for navigating via theshell user interface 62 in accordance with one aspect of the presentinvention. Beginning at step 1700, a first page is displayed by theshell user interface 62. A user requests a second page at step 1702(e.g., by selecting a link to the second page). If the first page is aplace, then step 1704 branches to step 1706, where the place, orinformation about the place, is written into the global queue 81 and/orthe appropriate application queue 82. The second page is then displayedat step 1708.

At step 1710, the user requests a third page via the shell userinterface 62. If the second page is a place, then step 1712 branches tostep 1714, where information about the second place is written into theglobal queue 81 and/or the respective application queue 82. The thirdpage is then displayed at step 1716.

The user selects the back button 104 at step 1718. Since the second pageis a place (step 1712), the shell component 64 accesses the travel log81, which directs the shell component 64 to display the second page 1720(described below with reference to FIG. 18). At step 1722, the backbutton 104 is selected again, and the first page, if it is a place (step1724), is displayed by the shell user interface 62 (step 1726). If,however, the first page is not a place, then step 1704 skips to 1708,and information about the first page is not written into the queue. Inaddition, when the back button 104 is selected at step 1722, the userinterface 62 does not navigate backward to the first page, but insteadeither advances to a previous place, or is handled appropriately inanother manner (e.g., does not respond or indicates that there are noprevious places).

Returning to step 1712, if the second page was not a place, then step1712 branches to step 1730 where the third page is displayed. The userthen selects the back button at step 1732. If the first page is a place,step 1734 branches to step 1736 where the first page is displayed. If,however, the first page is not a place, then step 1734 branches to step1728, where the selection is handled appropriately.

The navigation sequence shown in FIG. 17 is a simplified navigationexample. Navigation may continue beyond the sequence shown (e.g., byselecting the forward button 106 from either the first page or thesecond page), and may involve more complicated navigation steps as isdescribed above.

FIG. 18 shows a general process for reinstantiating a page instance 80in accordance with one aspect of the present invention. Beginning atstep 1800, a first page instance is displayed by the shell userinterface 62. At step 1802, a request is made by the user to navigateaway from the first page (e.g., by selecting an application link 112 foranother application). At 1804, the data object 76 for the page instanceis saved via implicit save. Information about the page instance'sPersistent Application Page 92 is then saved (e.g., written into theapplication queue 82 for the application) at step 1806.

After a navigation sequence, the user eventually requests that the pageinstance be displayed again at step 1808 (e.g., the user returns to theitem via navigation with the back and forward buttons 104, 106.

To retrieve a second page instance 80 as a result of a request via theshell user interface 62 (e.g., by selecting the “back” button), at step1810 the Persistent Application Page 92 is called and, in return, themoniker 96 retrieves the associated running data object 76. At step1812, the page code 74 is retrieved according to the pointerinformation. The running data object 76 and the page code 74 are thencombined to display the second page instance 80 in accordance with viewinformation dictated by the view selector 95 (steps 1814 and 1816).

FIG. 19 shows a representation of a method for creating command pages inaccordance with one aspect of the present invention. Beginning at step1900, commands and command groups are grouped according to the commandschema. The assembly mechanism 188 then, according to a particularcontext, begins generation of a command page by walking the commandsgraph from a node on the graph that is relevant to the particularcontext step of the application. If a filter is available, then step1904 branches to step 1906, where the filter is applied. If not, thenstep 1904 skips to step 1908. If user history is available, step 1908branches to step 1910, where the user history may be used to bubbleparticular commands or command groups to prominent locations on acommand page. If user history is not available or not enabled, then step1908 branches to step 1912, where the command page is created using thecommands, command groups, the filter, and/or the user history.

While the invention is susceptible to various modifications andalternative constructions, a certain illustrated embodiment thereof isshown in the drawings and has been described above in detail. It shouldbe understood, however, that there is no intention to limit theinvention to the specific form or forms disclosed, but on the contrary,the intention is to cover all modifications, alternative constructions,and equivalents falling within the spirit and scope of the invention.

1-44. (canceled)
 45. In a computer system having a graphical userinterface and a user interface selection device, a method of providingthe user interface for selection therefrom, comprising: maintainingcommand information about commands that are available for anapplication, the command information including textual information abouteach of the commands; providing an option for requesting some of thecommands in accordance with the command information; in response to asignal indicative of a selection of the option, rendering a command pagethat displays at least some of the commands; and for each of thecommands displayed on the command page, displaying the textualdescription along with the command.
 46. The method of claim 45, furthercomprising: maintaining user prior history information about thecommands; and displaying the commands on the command page in accordancewith the prior history information.
 47. The method of claim 46, whereindisplaying the commands on the command page in accordance with the priorhistory information comprises bubbling selected commands to selectedlocations on the command page.
 48. The method of claim 45, whereindisplaying at least some of the commands comprises displaying a link toa subset of the commands.
 49. The method of claim 45, furthercomprising: maintaining information about scopes available within theparticular context; providing a scope selector with a plurality of scopeselections; and in response to a signal indicating selection of one ofthe selections, providing the commands on the command page in accordancewith the information about scopes.
 50. The method of claim 45, whereinthe at least some commands are displayed in accordance with a context inwhich the option is selected.
 51. The method of claim 45, wherein thecommands that are displayed are restricted by a filter.
 52. The methodof claim 51, wherein the filter comprises a textual search.
 53. Acomputer-readable medium having computer-executable instructions forperforming the method recited in claim
 45. 54. In a computer systemhaving a graphical user interface and a user interface selection device,a method of providing the user interface for selection therefrom,comprising: maintaining command information about commands that areavailable for an application, the command information including groupinginformation about the commands; providing an option for requesting someof the commands in accordance with the command information; in responseto a signal indicative of a selection of the option, rendering a commandpage that displays at least some of the commands and a link to a groupof the commands.
 55. The method of claim 54, further comprising:maintaining user prior history information about the commands; anddisplaying the commands on the command page in accordance with the priorhistory information.
 56. The method of claim 55, wherein displaying thecommands on the command page in accordance with the prior historyinformation comprises bubbling selected commands to selected locationson the command page.
 57. The method of claim 54, wherein displaying atleast some of the commands further comprises displaying textualinformation about the at least some commands.
 58. The method of claim54, further comprising: maintaining information about scopes availablewithin the particular context; providing a scope selector with aplurality of scope selections; and in response to a signal indicatingselection of one of the selections, providing the commands on thecommand page in accordance with the information about scopes.
 59. Themethod of claim 54, wherein the at least some commands are displayed inaccordance with a context in which the option is selected.
 60. Themethod of claim 54, wherein the commands that are displayed arerestricted by a filter.
 61. The method of claim 60, wherein the filtercomprises a textual search.
 62. A computer-readable medium havingcomputer-executable instructions for performing the method recited inclaim
 54. 63. A computer-readable medium having stored thereon a datastructure, the data structure comprising: a first data field comprisingcommand information about a command; and a second data field associatedwith the command information comprising information corresponding to adescription of the command, the description capable of being sensed by auser.
 64. The computer-readable medium of claim 63, wherein the commandinformation comprises a short name for the command.
 65. Thecomputer-readable medium of claim 64, further comprising a third datafield associated with the command information comprising informationcorresponding to terms that are descriptive of the command and arecapable of being found by a search.
 66. The computer-readable medium ofclaim 63, wherein the description of the command comprises a textualdescription of the functions of the command.
 67. A computer readablemedium having stored thereon a data structure, the data structurecomprising: a first data field comprising command information about acommand; and a second data field associated with the command informationcomprising information corresponding to terms that are descriptive ofthe command and are capable of being found by a search.
 68. Thecomputer-readable medium of claim 67, wherein the command informationcomprises a short name for the command.
 69. The computer-readable mediumof claim 67, further comprising a third data field associated with thecommand information comprising information corresponding to adescription of the command, the description capable of being sensed by auser. 70-71. (canceled)